home *** CD-ROM | disk | FTP | other *** search
- Using the IBM Token-Ring Source Routing Driver
-
- This text explains the use of the IBM Token-Ring Source Routing Driver on
- NetWare networks. It does NOT replace the instructions for software
- generation contained in the NetWare installation manuals.
-
- The IBM Token-Ring Source Routing Driver enables NetWare communication across
- IBM Token-Ring network bridges.
-
-
- Guidelines for using the Source Routing Driver
-
- You should understand the following general guidelines before attempting to
- use the IBM Token-Ring Source Routing Driver on your NetWare network.
-
- o All stations that will access a server connected through an IBM Token-
- Ring network bridge must use the IBM Token-Ring Source Routing Driver.
-
- o All file servers and NetWare bridges connected through an IBM Token-Ring
- network bridge must use the same network address. The IBM Token-Ring
- network bridge is transparent to NetWare. Rings that are linked together
- through the bridge are viewed as one ring.
-
- NOTE: Do not confuse the ring number with the network address used when
- generating NetWare software. Network addresses for servers and
- bridges linked through IBM bridges must be the same, but each ring
- number must be unique.
-
- Using the Source Routing Driver with NetWare 386
-
- ROUTE.NLM is the driver that performs Source Routing on a NetWare 386 file
- server. ROUTE must be loaded on the file server before you set up
- workstations for source routing. Refer to ROUTENLM.TXT for instructions on
- loading ROUTE and setting parameters.
-
- To install source routing on workstations, complete the following steps.
-
- 1. Create a boot diskette with the NetWare v2.50 driver for the Token-Ring
- workstations.
-
- 2. Copy the ROUTE.COM file to the boot diskette.
-
- 3. Add the command to load ROUTE.COM to the AUTOEXEC.BAT file.
-
- NOTE: Steps 2 and 3 should have been completed when you prepared your Token-
- Ring boot diskettes.
-
- 4. Set the parameters for ROUTE.COM. See "Additional Information" on the
- next page for the parameters that ROUTE.COM can be loaded with. Add the
- parameter in the AUTOEXEC.BAT file.
-
- Additional Information
-
- The following parameters can be entered when ROUTE.COM is first loaded.
-
- BOARD = number
- MBR
- CLEAR
- NODES = number
- DEF
- REMOVE = number
- GBR
-
- The parameters can also be changed by loading ROUTE.COM a second time. For
- on-line help, type
-
- ROUTE ? <Enter>
-
- Most of the parameters have default values that should work with simple
- configurations for IBM bridges. If you have installed parallel IBM bridges,
- you can change some of the parameters to reduce traffic on some of the paths.
-
- Each parameter is described below.
-
- BOARD = number
-
- Use this parameter to specify a board number for the Token-Ring network
- board.
-
- o If this parameter is not specified, the default of 01 is used.
-
- o If you have loaded more than one LAN driver in the workstation, the board
- number is determined by the order the LAN drivers are loaded (the first
- board is 1). See your AUTOEXEC.BAT file for the order you have
- specified.
-
- CLEAR
-
- Use this parameter to manually clear the Source Routing table and force a
- dynamic rebuilding of the table by sending a default frame to each specific
- node in the network. Use this parameter when an IBM bridge on the network
- has gone down and an alternate route is available.
-
- DEF
-
- Use this parameter to prevent frames that have unknown (DEFault) destination
- addresses from being sent across Single Route IBM bridges.
-
- o If this parameter IS specified, ALL FRAMES that have addresses not
- currently in the workstation's Source Routing table will be forwarded as
- All Routes Broadcast FRAMES.
-
- o If this parameter is NOT specified, all frames that have addresses not
- currently in the workstation's Source Routing table will be forwarded as
- Single Route Broadcast frames.
-
- o If ROUTE.COM has ALREADY been loaded with the DEF parameter, reloading
- ROUTE.COM with this parameter broadcasts all subsequent Single Route
- Broadcast frames as All Routes Broadcast frames.
-
- GBR
-
- Use this parameter to specify that all General BRoadcast frames are to be
- sent as All Routes Broadcast frames.
-
- o If this parameter is NOT specified when ROUTE is loaded, all General
- Broadcast frames are broadcasted as Single Route Broadcast frames.
-
- o If ROUTE has ALREADY been loaded with the GBR parameter, reloading ROUTE
- with this parameter broadcasts all subsequent General Broadcast frames
- as All Routes Broadcast frames.
-
- MBR
-
- Use this parameter to specify that all Multicast BRoadcast frames are to be
- sent as All Routes Broadcast frames.
-
- o If the parameter is NOT specified when ROUTE is loaded, all Multicast
- Broadcast frames are broadcast as Single Route Broadcast frames.
-
- o If ROUTE has ALREADY been loaded with the MBR parameter, reloading ROUTE
- with this parameter broadcasts all subsequent Multicast Broadcast frames
- as All Routes Broadcast frames.
-
- NODES = number
-
- Use this parameter to specify the number of table entries in the Source
- Routing table. This parameter must be entered the first time ROUTE.COM is
- loaded. The parameter cannot be changed by reloading ROUTE.COM.
-
- Replace "number" with a value from 8 to 255. The default is 16.
-
- REMOVE = number
-
- Use this parameter to remove a specified node address from the workstation's
- Source Routing table. Use the parameter when a bridge has gone down.
- Removing the node from the Source Routing table forces the workstation to
- determine an alternate path.
-
- Replace "number" with a 12-digit (6-byte) hexadecimal number. If less than
- 9 digits are entered, ROUTE.COM prefixes the address with 4000h. For
- example, REMOVE=2 is interpreted as REMOVE=400000000002.
-
-
- Setting up the NetWare 286 file server or bridge for Source Routing
-
- If you have NetWare 286 file servers or bridges on your network and want to
- use Source Routing, you must configure them for Source Routing. The Source
- Routing file for NetWare 286 file servers and bridges is a VAP, and the VAP
- loads as the file server or bridge is booted. On a file server, NetWare 286
- searches for VAPs in the SYS:SYSTEM directory. On a bridge, NetWare checks
- the current drive for VAPs. VAPs with a numerical extension (.VP0, VP1,
- etc.) are loaded in numerical order. ROUTE.VP0 has a zero as its last number
- in the extension because it should be loaded first.
-
-
- To set up a NetWare 286 file server or bridge for Source Routing, you will
- need to complete the following tasks.
-
- o Configure ROUTE.VP0 for the appropriate LAN driver.
-
- o Copy ROUTE.VP0 to SYS:SYSTEM for a server or to the root directory for
- a bridge.
-
- o Down the file server or bridge and then reboot.
-
- To complete these tasks, complete the following steps.
-
- 1. If you want to change configuration parameters, use SRCONFIG. SRCONFIG
- is not required for most bridge applications, since ROUTE.VP0 is
- configured for most bridge applications.
-
- SRCONFIG <Enter>
-
- Follow the prompts.
-
- 2. Copy the ROUTE.VP0 file (that you have configured on the Bridge Services
- and Utilities diskette).
-
- o For a NetWare 286 file server, copy it to the SYS:SYSTEM directory
-
- o For a NetWare 286 bridge, copy it to the boot directory.
-
- 3. Down the file server or the bridge.
-
- 4. Reboot the file server or bridge. Answer the prompts so that the VAP
- loads.
-
- 5. If needed, configure the VAP with the specialized parameters. ROUTE.VP0
- loads a console command, ROUTE. With ROUTE, you can configure the
- NetWare 286 file server or bridge. Most of the ROUTE.NLM parameters can
- be used, with the following exceptions.
-
- UNLOAD: This parameter cannot be used with the VAP. You will need to
- reconfigure the VAP with SRCONFIG to remove Source Routing from
- a LAN driver. To remove Source Routing from LAN A but retain it
- for LAN B, use the following command.
-
- SRCONFIG <Enter>
-
- BOARD: Board number is determined by the LAN. LAN A is board 1; LAN B,
- 2; etc. LAN A is the default if no board number is specified in
- a command.
-
- Use the following format to enter a console command.
-
- ROUTE TIME=10 <Enter>
-
- This would change the TIME parameter on LAN A.
-
- To change the TIME parameter on LAN B, use the following format.
-
- ROUTE BOARD=B TIME=10 <Enter>
-
- NOTE: If you need to permanently configure the VAP with one of these
- parameters, use SRCONFIG with the following format.
-
- SRCONFIG <Enter>